Repository navigation
BREAKING CHANGE: Remove read-only SupportsScopeTags property from all resources - #6180
Merged
NikCharlebois merged 6 commits intoSep 23, 2025
Conversation
FabienTschanz
requested review from
M365DSCApprover,
NikCharlebois,
m365dscapproval and
ykuijs
as code owners
June 15, 2025 15:24
Collaborator
|
@FabienTschanz can you look at resolving the conflicts? |
Collaborator
Author
|
@NikCharlebois Conflicts fixed, waiting for unit tests. |
NikCharlebois
approved these changes
Sep 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Remove read-only
SupportsScopeTagsproperty from all resources. Additionally, cleanup the Intune resources from test mocks that are scattered throughout the test files into theBeforeAllpart of the test setup.This Pull Request (PR) fixes the following issues
None.
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).